Repository navigation
Fix getPower return value - #443
Merged
Merged
Conversation
Power level -3 returned the wrong value.
Owner
|
Good catch! thanks! |
h2zero
pushed a commit
that referenced
this pull request
Nov 3, 2026
… at low handles (#443) * feat(NimBLEServer): add registerServicesFirst() to place app services at low handles By default the standard GAP (0x1800) and GATT (0x1801) services register first and take the low attribute handles (0x0001+), with the application's services placed after them. Some peripherals must instead expose their own services at the low handles — e.g. when emulating a device whose central addresses attributes by hardcoded handle rather than by discovery. Add an opt-in NimBLEServer::registerServicesFirst(bool) setter (default false, so existing behavior is unchanged) that defers GAP/GATT registration until after the application services in resetGATT(), giving the application services the low handles. The device-name/appearance restore that follows ble_gatts_reset() is factored into a small lambda so it stays correct in either order.
h2zero
pushed a commit
that referenced
this pull request
Nov 3, 2026
… at low handles (#443) * feat(NimBLEServer): add registerServicesFirst() to place app services at low handles By default the standard GAP (0x1800) and GATT (0x1801) services register first and take the low attribute handles (0x0001+), with the application's services placed after them. Some peripherals must instead expose their own services at the low handles — e.g. when emulating a device whose central addresses attributes by hardcoded handle rather than by discovery. Add an opt-in NimBLEServer::registerServicesFirst(bool) setter (default false, so existing behavior is unchanged) that defers GAP/GATT registration until after the application services in resetGATT(), giving the application services the low handles. The device-name/appearance restore that follows ble_gatts_reset() is factored into a small lambda so it stays correct in either order.
h2zero
pushed a commit
that referenced
this pull request
Nov 4, 2026
… at low handles (#443) * feat(NimBLEServer): add registerServicesFirst() to place app services at low handles By default the standard GAP (0x1800) and GATT (0x1801) services register first and take the low attribute handles (0x0001+), with the application's services placed after them. Some peripherals must instead expose their own services at the low handles — e.g. when emulating a device whose central addresses attributes by hardcoded handle rather than by discovery. Add an opt-in NimBLEServer::registerServicesFirst(bool) setter (default false, so existing behavior is unchanged) that defers GAP/GATT registration until after the application services in resetGATT(), giving the application services the low handles. The device-name/appearance restore that follows ble_gatts_reset() is factored into a small lambda so it stays correct in either order.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Power level -3 returned the wrong value.